Methods for minimizing fragmentation in SSD within a storage system and devices thereof

ABSTRACT

A method, non-transitory computer readable medium, and device that assists with reducing memory fragmentation in solid state devices includes identifying an allocation area within an address range to write data from a cache. Next, the identified allocation area is determined for including previously stored data. The previously stored data is read from the identified allocation area when it is determined that the identified allocation area comprises previously stored data. Next, both the write data from the cache and the read previously stored data are written back into the identified allocation area sequentially through the address range.

FIELD

This technology generally relates to data storage management and, more particularly, methods for minimizing fragmentation in solid state devices (SSD) within a storage system and devices thereof.

BACKGROUND

Repeated writing data sets to, and erasing data sets from, a data storage medium causes storage space to be used inefficiently and this phenomenon is called fragmentation within the data storage medium. Fragmentation within the data storage mediums phenomenon reduces storage capacity, and increases access and read times. Fragmentation occurs when a computing device does not allocate enough contiguous storage space to encode a complete data set as a single sequence, and instead divides the data set into portions which are encoded in gaps between other data sets. Typically, these data storage medium gaps arise because an earlier data set was deleted, or excess space was allocated to another stored data set. The degree to which a data storage medium is fragmented heavily dependent upon the size and number of data sets stored on it.

To address the fragmentation issue, prior technologies uses the technique of defragmentation where the datasets written to a data storage medium is rearranged such that segments of each data set are written contiguously. Unfortunately, the technique used in the prior technologies fails to significantly reduce fragmentation and are time consuming, memory intensive operations that can significantly reduce the performance of a computer system while being executed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an environment with a storage management computing device that minimizes fragmentation in SSD within a storage system;

FIG. 2 is a block diagram of the exemplary storage management computing device shown in FIG. 1; and

FIG. 3 is an exemplary flow chart of an example of a method for minimizing fragmentation in SSD within a storage system.

DETAILED DESCRIPTION

An environment 10 with a plurality of client computing devices 12(1)-12(n), an exemplary storage management computing device 14, a plurality of storage devices 16(1)-16(n) is illustrated in FIG. 1. In this particular example, the environment 10 in FIG. 1 includes the plurality of client computing devices 12(1)-12(n), the storage management computing device 14 and a plurality of storage devices 16(1)-16(n) coupled via one or more communication networks 30, although the environment could include other types and numbers of systems, devices, components, and/or other elements. The example of a method for minimizing fragmentation in SSD within a storage system is executed by the storage management computing device 14, although the approaches illustrated and described herein could be executed by other types and/or numbers of other computing systems and devices. The environment 10 may include other types and numbers of other network elements and devices, as is generally known in the art and will not be illustrated or described herein. This technology provides a number of advantages including providing methods, non-transitory computer readable media and devices for minimizing fragmentation in SSD within a storage system.

Referring to FIG. 2, in this example the storage management computing device 14 includes a processor 18, a memory 20, and a communication interface 24 which are coupled together by a bus 26, although the storage management computing device 14 may include other types and numbers of elements in other configurations.

The processor 18 of the storage management computing device 14 may execute one or more programmed instructions stored in the memory 20 for dynamic resource reservation based on classified input/output requests as illustrated and described in the examples herein, although other types and numbers of functions and/or other operation can be performed. The processor 18 of the storage management computing device 14 may include one or more central processing units (“CPUs”) or general purpose processors with one or more processing cores, such as AMD® processor(s), although other types of processor(s) could be used (e.g., Intel®).

The memory 20 of the storage management computing device 14 stores the programmed instructions and other data for one or more aspects of the present technology as described and illustrated herein, although some or all of the programmed instructions could be stored and executed elsewhere. A variety of different types of memory storage devices, such as a non-volatile memory, random access memory (RAM) or a read only memory (ROM) in the system or a floppy disk, hard disk, CD ROM, DVD ROM, or other computer readable medium which is read from and written to by a magnetic, optical, or other reading and writing system that is coupled to the processor 18, can be used for the memory 20.

The communication interface 24 of the storage management computing device 14 operatively couples and communicates with the plurality of client computing devices 12(1)-12(n) and the plurality of storage devices 16(1)-16(n), which are all coupled together by the communication network 30, although other types and numbers of communication networks or systems with other types and numbers of connections and configurations to other devices and elements. By way of example only, the communication network 30 can use TCP/IP over Ethernet and industry-standard protocols, including NFS, CIFS, SOAP, XML, LDAP, and SNMP, although other types and numbers of communication networks, can be used. The communication networks 30 in this example may employ any suitable interface mechanisms and network communication technologies, including, for example, any local area network, any wide area network (e.g., Internet), teletraffic in any suitable form (e.g., voice, modem, and the like), Public Switched Telephone Network (PSTNs), Ethernet-based Packet Data Networks (PDNs), and any combinations thereof and the like. In this example, the bus 26 is a universal serial bus, although other bus types and links may be used, such as PCI-Express or hyper-transport bus.

Each of the plurality of client computing devices 12(1)-12(n) includes a central processing unit (CPU) or processor, a memory, and an I/O system, which are coupled together by a bus or other link, although other numbers and types of network devices could be used. The plurality of client computing devices 12(1)-12(n) communicates with the storage management computing device 14 for storage management, although the client computing devices 12(1)-12(n) can interact with the storage management computing device 14 for other purposes. By way of example, the plurality of client computing devices 12(1)-12(n) may run application(s) that may provide an interface to make requests to access, modify, delete, edit, read or write data within storage management computing device 14 or the plurality of storage devices 16(1)-16(n) via the communication network 30.

Each of the plurality of storage devices 16(1)-16(n) includes a central processing unit (CPU) or processor, and an I/O system, which are coupled together by a bus or other link, although other numbers and types of network devices could be used. Each plurality of storage devices 16(1)-16(n) assists with storing data, although the plurality of storage devices 16(1)-16(n) can assist with other types of operations such as storing of files or data. Various network processing applications, such as CIFS applications, NFS applications, HTTP Web Data storage device applications, and/or FTP applications, may be operating on the plurality of storage devices 16(1)-16(n) and transmitting data (e.g., files or web pages) in response to requests from the storage management computing device 14 and the plurality of client computing devices 12(1)-12(n). It is to be understood that the plurality of storage devices 16(1)-16(n) may be hardware such as hard disk drives, solid state devices (SSD), or magnetic tapes, or software or may represent a system with multiple external resource servers, which may include internal or external networks. While in this example it is illustrated that the plurality of storage devices 16(1)-16(n) are outside the storage management computing device 14, the plurality of storage devices 16(1)-16(n) can reside within the storage management computing device 14 in other examples.

Although the exemplary network environment 10 includes the plurality of client computing devices 12(1)-12(n), the storage management computing device 14, and the plurality of storage devices 16(1)-16(n) described and illustrated herein, other types and numbers of systems, devices, components, and/or other elements in other topologies can be used. It is to be understood that the systems of the examples described herein are for exemplary purposes, as many variations of the specific hardware and software used to implement the examples are possible, as will be appreciated by those of ordinary skill in the art.

In addition, two or more computing systems or devices can be substituted for any one of the systems or devices in any example. Accordingly, principles and advantages of distributed processing, such as redundancy and replication also can be implemented, as desired, to increase the robustness and performance of the devices and systems of the examples. The examples may also be implemented on computer system(s) that extend across any suitable network using any suitable interface mechanisms and traffic technologies, including by way of example only teletraffic in any suitable form (e.g., voice and modem), wireless traffic media, wireless traffic networks, cellular traffic networks, G3 traffic networks, Public Switched Telephone Network (PSTNs), Packet Data Networks (PDNs), the Internet, intranets, and combinations thereof.

The examples also may be embodied as a non-transitory computer readable medium having instructions stored thereon for one or more aspects of the present technology as described and illustrated by way of the examples herein, as described herein, which when executed by the processor, cause the processor to carry out the steps necessary to implement the methods of this technology as described and illustrated with the examples herein.

An example of a method for minimizing fragmentation in SSD within a storage system will now be described herein with reference to FIGS. 1-3. The exemplary method begins at step 305 where the storage management computing device 14 receives a data operation request, such as a read request or a write request by way of example, from one of the plurality of client computing devices 12(1)-12(n), although the storage management computing device 14 can receive other types and/or numbers of requests from other devices. In this particular example, the received data operation request includes a write request on an object, although the storage management computing device 14 can receive other types and/or numbers of data operation requests from other devices.

Next in step 310, the storage management computing device 14 caches the received write data operation into the cache within memory 20 of the storage management computing device 14, although the storage management computing device 14 can cache or otherwise store the operations at other memory locations.

Next in step 315, upon caching the received write data operation the storage management computing device 14 may determine when the cache within memory 20 has reached a threshold size. In this particular example, the cache within the memory 20 has a stored or otherwise set threshold size after which the cache cannot receive further data. Accordingly, when the storage management computing device 14 determines that the cache has not yet reached the threshold size, then the No branch is taken back to step 305 where the storage management computing device 14 continues to receive the data operation request from the plurality of client computing devices 12(1)-12(n).

However, if back in step 315 when the storage management computing device 14 determines that the cache is full, then the Yes branch is taken to step 320. In step 320, the storage management computing device 14 identifies an allocation area in one of the plurality of storage devices 16(1)-16(n) which is a solid state drive (SSD), although the storage management computing device 14 can identify the allocation area at other memory locations, such as in memory 20. In this example, allocation area relates to the memory space in the SSD where the contents from the cache could be transferred. Additionally in this example, the storage management computing device 14 includes metadata stored in the memory 20 that includes the address range in the memory strip within the SSD that can stage the data being flushed out of the cache within the memory 20. The storage management computing device 14 may use the metadata to identify the allocation area, although the storage management computing device 14 can use other types and/or amounts of information to identify the allocation area. Further in this example, the size allocation area identified by the storage management computing device 14 is at least equal to the size of the data in the cache that is going to be transferred, although the size of the allocation area can be more than the size of the data being transferred. Furthermore, the address range of the identified allocation area can include a combination of free space and previously stored data (due to fragmented data that was previously stored) in this example.

Next in step 325, the storage management computing device 14 determines or identifies the amount of data in the cache that can be transferred to the identified allocation area sequentially from the starting of the address range of the identified allocation area to the end of the address range of the identified allocation area.

In step 330, during the traversing the storage management computing device 14 determines when there is data stored in the address range of the identified allocation area, although the storage management computing device 14 can use other techniques to make the determination. In this example, the allocation area identified by the storage management computing device 14 can include data that was previously transferred from the cache within memory 20, although the identified allocation area can include other types and/or amounts of data. Accordingly, when the storage management computing device 14 determines that the data is present in the address range, then the Yes branch is taken in to step 335.

In step 335, the storage management computing device 14 reads the previously stored data in the address range of the allocation area. In this example, the storage management computing device 14 is required to read the previously stored data within the address range in the allocation area as the data has to be first read before writing the data back into the SSD.

Next in step 340, the storage management computing device 14 combines the read data from step 335 with the cache data that is required to be transferred to the allocation area, although the storage management computing device 14 can add other types and/or amounts of information.

Next in step 345, the storage management computing device 14 writes or transfers the data present in the cache within the memory 20 and the previously stored data that was read back into the identified allocation area within the SSD. Additionally back in step 330, when the storage management computing device 14 determines that there was no data found during the traversing, then the No branch is taken to this step 345. When the exemplary flow proceeds to step 345 with no data in the address range of the identified allocation area, then the storage management computing device 14 only writes or transfers the data from the cache within memory 20 to the identified allocation area. In this example, the storage management computing device 14 begins the write or transfers the data from the start of the address range of the identified allocation and proceeds to write or transfer the data sequentially in the address range. By writing the data into the allocation area sequentially, the technology is able to reduce the fragmentation in the SSD within the plurality of storage devices 16(1)-16(n) and the exemplary method ends at step 350.

Accordingly, as illustrated and described by way of the examples herein, this technology provides a number of advantages including providing methods, non-transitory computer readable media and devices for minimizing fragmentation in SSD within an enterprise storage system. By writing the data sequentially into the allocation area in the SSD, the technology able to significantly reduce the fragmentation in SSD thereby increases the memory utilization of the SSD.

Having thus described the basic concept of the technology, it will be rather apparent to those skilled in the art that the foregoing detailed disclosure is intended to be presented by way of example only, and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested hereby, and are within the spirit and scope of the technology. Additionally, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes to any order except as may be specified in the claims. Accordingly, the invention is limited only by the following claims and equivalents thereto. 

What is claimed is:
 1. A method comprising: reading, by a computing device, previously stored data in an identified allocation area within an address range in one of a plurality of non-volatile storage device upon determining that a cache memory is full, wherein the identified allocation area comprises the previously stored data transferred from the cache, and wherein a size of the identified allocation area is at least equal to the size of the cache; and writing, by the computing device, the data from the cache and the read previously stored data back into the identified allocation area sequentially from starting of the address range.
 2. The method as set forth in claim 1 further comprising writing, by the computing device, only write data from the cache to the identified allocation area sequentially through the address range when the previously stored data is not determined to be present in the identified allocation area.
 3. The method as set forth in claim 1 further comprising receiving, by the computing device, a write data operation from a client computing device.
 4. The method as set forth in claim 3 further comprising: caching, by the computing device, the received write data operation in the cache.
 5. The method as set forth in claim 3 further comprising, determining, by the computing device, when the cache has reach a threshold memory size.
 6. The method as set forth in claim 5 further comprising identifying, by the computing device, the allocation area to transfer the data from the cache when the cache is determined to have reached the threshold memory size.
 7. A non-transitory computer readable medium having stored thereon instruction for reducing fragmentation in solid state devices (SSD) comprising executable code which when executed by a processor, causes the processor to perform steps comprising: reading, by a computing device, previously stored data in an identified allocation area within an address range in one of a plurality of non-volatile storage device upon determining that a cache memory is full, wherein the identified allocation area comprises the previously stored data transferred from the cache, and wherein a size of the identified allocation area is at least equal to the size of the cache; and writing, by the computing device, the data from the cache and the read previously stored data back into the identified allocation area sequentially from starting of the address range.
 8. The medium as set forth in claim 7 further comprising writing only write data from the cache to the identified allocation area sequentially through the address range when the previously stored data is not determined to be present in the identified allocation area.
 9. The medium as set forth in claim 7 further comprising receiving a write data operation from a client computing device.
 10. The medium as set forth in claim 9 further comprising: caching the received write data operation in the cache.
 11. The medium as set forth in claim 9 further comprising, determining, when the cache has reach a threshold memory size.
 12. The medium as set forth in claim 11 further comprising identifying the allocation area to transfer the data from the cache when the cache is determined to have reached the threshold memory size.
 13. A storage management computing device comprising: a processor; a memory coupled to the processor which is configured to be capable of executing programmed instructions comprising and stored in the memory to: read, by a computing device, previously stored data in an identified allocation area within an address range in one of a plurality of non-volatile storage device upon determining that a cache memory is full, wherein the identified allocation area comprises the previously stored data transferred from the cache, and wherein a size of the identified allocation area is at least equal to the size of the cache; and write, by the computing device, the data from the cache and the read previously stored data back into the identified allocation area sequentially from starting of the address range.
 14. The device as set forth in claim 13 wherein the processor coupled to the memory is further configured to be capable of executing at least one additional programmed instruction comprising and stored in the memory to write only write data from the cache to the identified allocation area sequentially through the address range when the previously stored data is not determined to be present in the identified allocation area.
 15. The device as set forth in claim 13 wherein the processor coupled to the memory is further configured to be capable of executing at least one additional programmed instruction comprising and stored in the memory to receive a write data operation from a client computing device.
 16. The device as set forth in claim 15 wherein the processor coupled to the memory is further configured to be capable of executing at least one additional programmed instruction comprising and stored in the memory to: cache the received write data operation in the cache.
 17. The device as set forth in claim 15 wherein the processor coupled to the memory is further configured to be capable of executing at least one additional programmed instruction comprising and stored in the memory to determine when the cache has reach a threshold memory size.
 18. The device as set forth in claim 17 wherein the processor coupled to the memory is further configured to be capable of executing at least one additional programmed instruction comprising and stored in the memory to identify the allocation area to transfer the data from the cache when the cache is determined to have reached the threshold memory size. 